Fix bad_weak_ptr when close a ClientConnection during construction #350
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #348
Fixes #349
Motivation
When
close
is called inClientConnection
's constructor,shared_from_this()
will be called, which results in astd::bad_weak_ptr
error. This error does not happen before#317 because
shared_from_this()
could only be called when theproducers
orconsumers
field is not empty.Modifications
Add a
ResultException
and throw it if there is a failure inClientConnection
's constructor and catch it inConnectionPool::getConnectionAsync
. Then retrieve the result andreturn the failed future.
Since
close
is now always called on a constructedClientConnection
object, remove the 2nd parameter.
In addition, check
authentication_
even for non-TLS URLs. Otherwise,the null authentication will be used to construct
CommandConnect
.Add
testInvalidPlugin
andtestTlsConfigError
to verify the changes.